Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

[VMC on AWS] Inter SDDC Communication using Route Based VPN (76861)

Last Updated: 11/2/2023Categories: How toTotal Views: 239Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Purpose

To enable communication from one SDDC to another SDDC by configuring a Route-Based VPN.

Resolution

The communication between two SDDCs is done by creating a Virtual Private Network (VPN).

One VPN on each of the two SDDCs should be created with relevant fields.

The following is the procedure to create a Route Based VPN for SDDC to SDDC communication.

Log in to the VMC Console at https://vmc.vmware.com

Select the first SDDC from the console.

Navigate to the Networking & Security > VPN > Route Based.

Click ADD VPN and give the new VPN a Name.

Select a Local IP Address for the VPN.

Enter the Remote Public IP address of the second SDDC.

For BGP Local IP/Prefix Length, enter the IP address, in CIDR format, of the local VPN tunnel.

Choose a network of size of /30 from the 169.254.0.0/16 subnet. The second and third IP addresses in this range are configured as the remote and local VTI (VPN Tunnel Interface).

For BGP Remote IP, enter the BGP interface address of the second SDDCs VPN gateway.

This address must be a valid host IP on the subnet defined by the IP and Prefix Length you supplied and must not be the same as the BGP Local IP.

For BGP Remote ASN, enter the ASN of the second SDDC VPN gateway.

Configure Advanced Tunnel Parameters which include Tunnel encryption, Tunnel Digest Algorithm, Perfect Forward Secrecy, IKE Encryption, IKE Digest Algorithm, IKE Type,Diffie Hellman, Preshared Key, Remote Private IP .

6. (Optional) Under Advanced BGP Parameters, enter a BGP Secret that matches the one used by the second SDDC.

7. Click Save.

8. Navigate to the second SDDC > Network and Security > VPN > Route-based.

9. Click on Add VPN and fill in the name for the VPN. Also, fill in the Local IP address, Remote Public IP, BGP Local IP/Prefix Length, BGP Remote IP, BGP Remote ASN.

10. Configure the same Advanced Tunnel Parameters as done for step 5. Ensure that the Preshared Key is correct and click on Save.

As the Route Based VPN is created from the two SDDCs, it is now possible to communicate between the two SDDCs.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Cloud on AWS

Related Versions:

Take Our Survey

Support Assistant